home *** CD-ROM | disk | FTP | other *** search
- Path: nntp.teleport.com!usenet
- From: GHouck <hksys@teleport.com>
- Newsgroups: comp.lang.c
- Subject: Re: SCANF and FSCANF
- Date: 20 Apr 1996 08:26:50 GMT
- Organization: systems hk
- Message-ID: <4la74a$7tq@nadine.teleport.com>
- References: <4l61li$bu7@abel.cc.sunysb.edu>
- NNTP-Posting-Host: ip-pdx03-45.teleport.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 1.22 (Windows; I; 32bit)
-
- dkat@psych1.psy.sunysb.edu (DK) wrote:
- >Ok, this is driving me nuts. Why do I keeps seeing references to the
- >use of SCANF and FSCANF? Why would anyone use them or recommend their
- >use? Yes it saves one line of code but I see more people running into
- >problems they could easily avoid just by using gets and fgets followed
- >with sscanf and doing it consistently (Mixing gets, fgets, scanf, and
- >fscanf is another problem in itself)! Am I missing something?
- >
-
- I, for one, am sometimes (often?) lazy. Depends on how many lines of
- code I am interested in writing, and how long the program is going to
- last in this world, and how robust it needs to be. Nothing more.
- Nothing less. Kind of like: why would anybody use a bubble sort?
- Because it works under the right circumstances. So do scanf and fscanf.
-
- Yours, Geoff Houck
-
-